Communication between a document editor in-space user interface and a document editor out-space user interface

ABSTRACT

An out-space actuator is selected to access an out-space user interface for a document editor program. An out-space actuator is associated with an in-space user interface having a displayed document. When the out-space actuator is selected, an out-space user interface is displayed that includes an expanded feature selection surface. The out-space user interface may be used to display one or more status panes for providing status information about a document being edited in the in-space user interface. Application features for affecting changes to a given document&#39;s status may be exposed in the out-space interface in proximity to associated status information. An out-space communication user interface (UI) component may be temporarily displayed in the document in-space user interface to communicate document status information that is presently available in the out-space user interface. A message bar may be displayed in the in-space user interface for communicating information from the out-space user interface.

RELATED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 12/163,758, filed Jun. 27, 2008, and entitled “COMMUNICATIONBETWEEN A DOCUMENT EDITOR IN-SPACE USER INTERFACE AND A DOCUMENT EDITOROUT-SPACE USER INTERFACE,” which is indicated to grant as U.S. Pat. No.8,484,578, on Jul. 9, 2013, which was a continuation-in-part of U.S.patent application Ser. No. 11/823,999, filed Jun. 29, 2007 and entitled“ACCESSING AN OUT-SPACE USER INTERFACE FOR A DOCUMENT EDITOR PROGRAM,”which was granted at U.S. Pat. No. 8,201,103, on Jun. 12, 2012, all ofwhich are incorporated herein by reference as if fully set out herein.

BACKGROUND

In many document editors, authoring features, such as text and dataentry features, formatting features, and the like, are available via oneor more readily available feature menus. However, non-authoringfeatures, such as document security management, file format conversion,and document editing permissions management, are often difficult tolocate. In addition, when a user determines a non-authoring status of agiven document, for example, whether the document is in “read-only”mode, an application feature for changing the non-authoring status maybe difficult to locate and use. In addition, when a given type of statusfor a document changes, for example, when the document is being editedby another user, a present user may not know that the status of thedocument has changed.

It is with respect to these and other considerations that the presentinvention has been made.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key and/oressential features of the claimed subject matter. Also, this Summary isnot intended to limit the scope of the claimed subject matter.

Embodiments of the present invention solve the above and other problemsby providing access to document information and status and relatedfeatures/functionalities via an out-space user interface for a documenteditor program. An out-space actuator is associated with an in-spaceuser interface having a displayed document. When the out-space actuatoris selected, an out-space user interface is displayed that includes adisplay surface for displaying document information and status and forexposing non-authoring features and functionalities.

According to one embodiment, the out-space user interface may be used todisplay one or more status panes for providing status information abouta document being edited in the in-space user interface. According toanother embodiment, application features for affecting changes to agiven document's status may be exposed in the out-space interface inproximity to associated status information.

According to another embodiment, an out-space communication userinterface (UI) component may be temporarily displayed in the documentin-space user interface to communicate document status information thatis presently available in the out-space user interface. The out-spaceactuator may be displayed in the out-space communication UI component toallow a user to selectively display the out-space UI to receiveadditional information and/or features or functionality associated withthe document status information. According to one embodiment, a documentstatus pane displayed in the out-space user interface associated withthe information displayed in the out-space communication UI componentmay be visually highlighted to call a user's attention to a documentstatus pane associated with the information displayed in the out-spacecommunication user interface component.

According to another embodiment, a message bar may be displayed in thein-space user interface for communicating information from the out-spaceuser interface. An out-space actuator may be displayed in the messagebar for visually associating the message bar with the out-space userinterface and for allowing a user to selectively launch the out-spaceuser interface for obtaining additional information and/or functionalityor features associated with the document status information communicatedfrom the out-space user interface via the message bar displayed in thein-space user interface.

These and other features and advantages which characterize the presentinvention will be apparent from a reading of the following detaileddescription and a review of the associated drawings. It is to beunderstood that both the foregoing general description and the followingdetailed description are explanatory only and are not restrictive of theinvention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the present invention aredescribed with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 represents one example of an in-space user interface having anout-space actuator

FIG. 2 represents one example of an out-space user interface having adocument information tab:

FIG. 3 represents one example of an out-space user interface having adocument log tab;

FIG. 4 represents one example of an out-space user interface having ashare document tab;

FIG. 5 represents one example of an out-space user interface having aprint document tab;

FIG. 6 represents one example of an out-space user interface having agetting started tab;

FIG. 7 represents one example of an out-space user interface having aapplication information tab;

FIG. 8 represents one exemplary operational flow diagram for accessingan out-space user interface in a document editor program;

FIG. 9 represents one example of an out-space user interface showing anumber of document status information panes and associated applicationfeature selection controls;

FIG. 10 represents one example of an out-space user interface showing anumber of document status information panes and associated applicationfeature selection controls;

FIG. 11 represents one exemplary operation flow diagram for accessingdocument status and associated application features via an out-spaceuser interface in a document editor program;

FIG. 12 represents one example of an in-space user interface having anout-space communication user interface component and having an improvedmessage bar user interface component;

FIG. 13 represents one example of an out-space user interface showing anumber of document status information panes and associated applicationfeature selection controls;

FIG. 14 represents one exemplary operational flow diagram for receivinga communication of document status via an out-space communication userinterface component, and via an improved message bar user interfacecomponent; and

FIG. 15 represents an exemplary computing device with which embodimentsof the present invention may be practiced.

DETAILED DESCRIPTION

Embodiments are described more fully below with reference to theaccompanying drawings, which form a part hereof, and which show specificexemplary embodiments. However, embodiments may be implemented in manydifferent forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope. Embodiments may be practiced as methods, systems ordevices. Accordingly, embodiments may take the form of an entirelyhardware implementation, an entirely software implementation or animplementation combining software and hardware aspects. The followingdetailed description is, therefore, not to be taken in a limiting sense.

The logical operations of the various embodiments are implemented (1) asa sequence of computer implemented steps running on a computing systemand/or (2) as interconnected machine modules within the computingsystem. The implementation is a matter of choice dependent on theperformance requirements of the computing system implementing theinvention. Accordingly, the logical operations making up the embodimentsdescribed herein are referred to alternatively as operations, steps ormodules.

Embodiments of the invention are directed to accessing an out-space userinterface from an in-space user interface of a document editor.According to one embodiment, the out-space user interface is aninterface that includes a category of features that do not require adocument to be present on the display surface. According to anotherembodiment, an out-space user interface is a user-interface thatincludes non-authoring system features for a document editor program.The out-space user interface provides features to allow a user to dosomething with the document. In one aspect, the features do not affectthe content of the document. As an example, out-space features mayinclude document information features, document log features, printfeatures, getting started features, and application informationfeatures. As other examples, out-space features may include a newfeature, an open feature, a save feature, a close feature, a documentinspector feature, a send for review feature, a mark as final feature, apermissions feature, a template feature, a PDF feature, documentproperties, a package for CD feature, an encryption feature, an onlinefeature, an assign document tasks feature, an options feature, a publishto server feature, related document links, a digital signature, a blogfeature, a compatibility checker, a fax feature, a document workspace,versioning, check in/out services, and workflow services. Other examplesof out-space features may include tagging, workspaces/projects, relateddocument and information features, access to sharing features, branding,people and groups, community connections and file searches. Theaforementioned are but a few examples of out-space features. Out-spacefeatures may include any non-authoring features that do not require theuser to see the document while working with the features. In one aspect,the out-space user interface only includes non-authoring features thatdo not affect the content of the document. In another aspect, theout-space user interface does not include authoring features.

According to one embodiment, the out-space user interface may be used todisplay one or more document status panes or slabs which are userinterface components for displaying document status information, forexample, document security management status, document file formatstatus information, information about one or more other users havingaccess to a given document, whether a document contains digitalsignatures, whether previous versions of the document are available,whether the document is set to a particular edit mode, for example,“read-only,” and the like.

According to another embodiment, application features and/orfunctionalities for affecting changes to document status may be exposedin proximity to displayed document status in the form of a selectablebutton or control for allowing a user to selectively affect changes todisplayed document status via an associated application feature.Alternatively, information about how a given application feature orfunctionality may be applied to an associated document status may bedisplayed with the document status.

According to another embodiment, an out-space communication userinterface (UI) component may be temporarily displayed in the documentin-space user interface to communicate document status information thatis presently available in the out-space user interface. The out-spaceactuator may be displayed in the out-space communication UI component toallow a user to selectively display the out-space UI to receiveadditional information and/or features or functionality associated withthe document status information. According to one embodiment, a documentstatus pane displayed in the out-space user interface associated withthe information displayed in the out-space communication UI componentmay be visually highlighted to call a user's attention to a documentstatus pane associated with the information displayed in the out-spacecommunication user interface component.

According to still another embodiment, a message bar may be displayed inthe in-space user interface for communicating information from theout-space user interface. An out-space actuator may be displayed in themessage bar for visually associating the message bar with the out-spaceuser interface and for allowing a user to selectively launch theout-space user interface for obtaining additional information and/orfunctionality or features associated with the document statusinformation communicated from the out-space user interface via themessage bar displayed in the in-space user interface.

In contrast to the out-space user interface, an in-space user interfaceis a user interface that includes authoring features for authoring orchanging the content of a document. The affects of an in-space featureshow up on the document that is being authored. An in-space userinterface may include home features, insert features, page layoutfeatures, reference features, mailing features, review features and viewfeatures. An in-space user interface may also include formattingfeatures and writing tools. Other examples of in-space user interfacefeatures may include text features, picture features, tables, shapes,chat features, bold features, font features, layout features, arrangingfeatures, style features, find tools, spelling tools, a paste tool, aword count, and a synonym finder. These examples are but a few examplesof in-space features. In-space features may include any authoringfeature for authoring or changing the content of a document.

As set forth herein, a user may open a document editor to author adocument. A document editor may include a word processing editor, aspreadsheet editor, a slide presentation editor, a web page editor, anemail editor and/or any other type of editor for editing a document.Although a document editor is described herein, an out-space userinterface may also be associated with non-editing programs such as abrowser, a web page, an email application, a project application, etc.When a document editor is opened, the user may author a document usingthe in-space user interface. When the user decides to perform anon-authoring feature the user may select an out-space actuator. Uponselection, the document is removed from the display and the ribbon isexpanded to provide display space for the rich out-space features. Inanother aspect, the ribbon is replaced with an expanded featureselection surface. In still another aspect, the document is converted toan image, thumbnail, or miniature bitmap and moved to the out-space userinterface. In yet another aspect, the entire in-space user interface isconverted to an image, thumbnail, or miniature bitmap and moved to theout-space user interface. In this manner, the user has reassurance thatthey are not leaving the document editor program. If the user desiresreturning to the in-space user interface, the document image may beselected. Upon selection, the in-space user interface is repopulated onthe display.

By providing navigation between in-space and out-space, users may easilybecome familiar with out-space features because they are separated fromauthoring features. By separating in-space and out-space features, usersmay easily find features because the features are categorized. Featuresmay be richer and provide more information and functionality because the“real estate” of the display is better utilized. A greater amount of“real estate” is available for out-space features, thereby allowingsoftware developers the opportunity to increase the functionality of adocument editor program. Channels of communication associated with adocument are better managed because they are not mixed in with in-spacefeatures.

FIG. 1 represents one example of a primary or in-space user interfacehaving an out-space actuator. Document editor 100 includes ribbon 102,document 104 and out-space actuator 106. Document editor 100 may includea word processing editor, a spreadsheet editor, a slide presentationeditor, a web document editor, an email editor and/or any other type ofeditor for editing a document. Document editor may be associated with acomputing device, such as the exemplary computing device set forth inFIG. 9.

Ribbon 102 includes a plurality of ribbon tabs such as home tab, inserttab, page layout tab, references tab, mailings tab, review tab, viewtab, and/or any other type of authoring tab. Ribbon 102 may also includefeatures associated with the tab. For example, ribbon 102 depicts a hometab having clipboard features, font features, paragraph features, stylefeatures, and editing features. The tabs and features depicted in FIG. 1are but examples of tabs and features. Ribbon 102 may include any typeof authoring tabs and features depending on the type of document 104being authored.

Document 104 may be located below ribbon 102. Document 104 may be a“live” document that allows a user to edit and author the content ofdocument 104. Document 104 may include a word processing document, aslide presentation document, a spreadsheet document, an internetdocument, an email document, and/or any other type of document that maybe authored.

Out-space actuator 106 may include any type of button or selector. Eventhough out-space actuator 106 is depicted in the upper left corner ofdocument editor 104, out-space actuator may be located anywhere indocument editor 104. In one aspect, out-space actuator 106 provides“one-click” actuation of an out-space user interface. In this manner, auser is not required to navigate drop-down menus or lists to findout-space features.

FIG. 2 represents one example of a secondary or out-spacecomputer-generated user interface having a document information tab.Even though FIGS. 2-7 depicts tabs along the top of document editor 200,the tabs may be located on the sides, bottom and/or any other locationwithin document editor. The tabs may also include buttons, quick linksand/or other features not specifically depicted in FIG. 2-7. Documenteditor 200 includes expanded ribbon 202, document image 204 andout-space actuator 206. Expanded ribbon 202 includes a plurality ofribbon tabs such as a document information tab, a document log tab, ashare document tab, a print document tab, a getting started tab, and anapplication information tab. As shown in FIG. 2, expanded ribbon 202includes a greater display area than ribbon 102 of FIG. 1. In oneaspect, expanded ribbon 202 populates the display area that was utilizedby document 104 before document 104 was removed from the display area.In another aspect, expanded ribbon 202 includes buttons andfunctionality that allows the user to work in expanded ribbon 202.

Document image 204 may include an image, a thumbnail, and a miniaturebitmap of document 104. In another aspect, the entire in-space userinterface is converted to an image, thumbnail, or miniature bitmap andmoved to the out-space user interface. Document image 204 may be staticor “non-live.” Stated another way, a user may not be able to authordocument image 204 while in the out-space user interface. In one aspect,document 104 is converted to document image 204 when out-space actuator106 is selected. In another aspect, document image 204 is displayed inexpanded ribbon 202. In still another aspect, document image may providea link back to the in-space user interface depicted in FIG. 1. Statedanother way, a user may navigate back to the in-space user interface ofFIG. 1 by selecting document image 204. Document image 204 may provide“one-click” actuation of an in-space user interface. In this manner, auser is not required to navigate drop-down menus or lists to findin-space features. In other aspects, out-space actuator 206 or any othertype of button or selector may be selected to navigate back to thein-space user interface.

As depicted in FIG. 2, document editor 200 may include documentinformation tab. Document information tab may be associated withdocument image 204, quick features 208, document details pane 210,document task list pane 212, dates pane 214, related items pane 216, andpeople pane 218. Quick features 208 may include a new feature, an openfeature, a save feature, a save-as feature, a close document feature,and an exit editor feature. Document details pane 210 may include fieldsfor entering metadata related to document 104. Such fields may include atitle field, subject field, abstract field, author field, page numberfield, and a word count field. Document task list pane 212 may include alist of reminder tasks and fields for completing a project. Dates panemay include a set of fields for populating dates associate withbenchmarks for a project. Related items pane 216 may include a list ofitems and fields for populating related items in document 104. Forexample, a related item may include a link to a webpage. People pane 218may include a set of fields for providing access levels to peopleassociated with document 104. For example, an access level may includeno access, full access or partial access.

FIG. 3 represents one example of an out-space user interface having adocument log tab. Document editor 300 includes expanded ribbon 302,document image 304 and out-space actuator 306. As depicted in FIG. 3,document editor 300 may include document log tab. Document log tab maybe associated with document image 304 and document log pane 308.Document log pane 308 may include a list and fields associated withevents related to a document. For example, documents log pane 308 mayinclude a list of print dates, saving dates, sharing dates and/or anyother document events that may be relevant in a log.

FIG. 4 represents one example of an out-space user interface having ashare document tab. Document editor 400 includes expanded ribbon 402,document image 404 and out-space actuator 406. As depicted in FIG. 4,document editor 400 may include share document tab. Share document tabmay be associated with document image 404, sharing task menu 408 andsharing pane 410. Share task menu 408 may include several features forsharing the document with other users. Sharing pane 410 may include aset of fields and functions for sharing the document. Sharing task menumay include sending pane 412, feedback pane 414, collaboration pane 416,and publishing pane 418. Sending pane 412 may include a send asattachment feature, a use document as message body feature, and/or asend document as fax feature. Feedback pane 414 may include a collectfeedback feature, which routes the document to several people. Feedbackpane 414 may also include a seek approval feature, which routes thedocument to several people and asks them to accept or reject thedocument. Feedback pane 414 may also include a send and track changesfeatures, which emails a copy of the document and asks others to proposechanges to include in the document. Collaboration pane 416 may include aworkspace collaboration feature, which assigns owners to sections of thedocument. Collaboration pane 416 may also include a server collaborationfeature, which invites others to access a shared copy of the document.Publishing pane 418 may include a publish to blog feature and a publishto management server feature.

FIG. 5 represents one example of an out-space user interface having aprint document tab. Document editor 500 includes expanded ribbon 502,document image 504 and out-space actuator 506. As depicted in FIG. 5,document editor 500 may include print document tab. Print document tabmay be associated with document image 504 and print menu pane 508. Printmenu 508 may include page layout pane 510, printer options pane 512,print selection pane 514, and print options pane 516. Page layout pane510 may include a margins feature, an orientation feature, a sizefeature, a shrink page feature, and a view feature. Printer options pane512 may include a field for selecting a printer and data associated withthe status, type and location of the printer. Print selection pane 514may include fields for selecting a portion of the document to print.Print options pane 516 may include fields for selecting how the documentshould be printed.

FIG. 6 represents one example of an out-space user interface having agetting started tab. Document editor 600 includes expanded ribbon 602and out-space actuator 604. Expanded ribbon 602 may not include adocument image in that the getting started tab indicates that a documenthas not been generated yet. As depicted in FIG. 6, document editor 600may include getting started tab. Getting started tab may be associatedwith recent documents pane 606 and template pane 608. Recent documentpane 606 may include a list of recently access documents. Templates pane608 may include a plurality of selectable templates. In one aspect, theselectable templates are thumbnails and upon selection, the in-spaceuser interface is automatically populated. Stated another way, the useris taken from the out-space user interface to the in-space userinterface because the selection of a template indicates that the userdesires authoring a document.

FIG. 7 represents one example of an out-space user interface having anapplication information tab. Document editor 700 includes expandedribbon 702 and out-space actuator 704. Expanded ribbon 702 may or maynot include a document image depending on whether the document has beencreated. As depicted in FIG. 7, document editor 700 may includeapplication information tab. Application information tab may beassociated with service pane 706. Service pane 706 may include onlineservices associated with the document editor. Service pane 706 mayinclude password features, online events, product trials, help features,security updates, diagnostics, training, etc.

FIG. 8 represents one exemplary operational flow diagram for accessingan out-space user interface in a document editor program. Operationalflow 800 begins at start operation 802 and continues to operation 804where an in-space interface is provided that includes an out-spaceactuator. An example of an in-space interface may include FIG. 1.Operational flow 800 continues to decision operation 806 where it isdecided whether to enter out-space. If not, operational flow 800continues to decision operation 808 where it is determined whether toexit the document editor. If it is decided to exit the document editor,operational flow continues to end operation 820. If it is decided to notexit the document editor, operational flow 800 loops back.

If it is decided to enter out-space, operational flow 800 continues tooperation 810 where the out-space actuator is selected. When theout-space actuator is selected, the document is converted to an image,the ribbon is expanded and out-space features are populated in the userinterface as indicated by operation 812. In another aspect, a documentimage is not created.

Operational flow continues to decision operation 814 where it is decidedwhether to return to in-space. If not, operational flow 800 continues todecision operation 818 where it is determined whether to exit thedocument editor. If it is decided to exit the document editor,operational flow continues to end operation 820. If it is decided to notexit the document editor, operational flow 800 loops back. If it isdecided to enter in-space, operational flow 800 continues to operation816 where the document image is selected. In another aspect, an in-spaceactuator is selected. Operational flow 800 then loops back to operation804.

FIG. 9 represents one example of an out-space user interface showing anumber of document status information panes and associated applicationfeature selection controls. As illustrated in FIG. 9, a document statustab 905 is provided for displaying status information about the documentbeing edited in the application in-space. As should be appreciated, thedocument status tab 905 is for illustration purposes only and is notlimiting of the different types and locations of selectable controls forcausing a display of document status information in the expanded ribbon202, described herein. As should be appreciated, the document editor 200may be configured for automatically displaying the document statusinformation, illustrated in FIG. 9, upon actuation of the out-spaceactuator 206.

Referring still to FIG. 9, a number of document status panes or slabs910, 912, 914, 916, 918 are displayed. The document panes 910-918 areillustrative of user interface components in which various types ofdocument status may be displayed in association with a document beingedited in the document editor in-space.

According to one embodiment, features and/or functionalities associatedwith displayed document status may be exposed in proximity to thedisplayed document status for selectively accessing the associatedfeatures and/or functionalities for affecting changes to a givendocument status. As illustrated in FIG. 9, selectable controls 911, 913,915, 917, 919, 920 are illustrated as being displayed inside associateddocument status panes for selectively accessing features for affectingchanges to document status displayed in the associated document panes910-918. Accordingly, if a given type of document status is displayed ina document pane, for example, pane 910, and if an application feature orfunctionality is available for affecting a change to the displayeddocument status, a selectable control 911 may be displayed in thedocument pane for accessing the associated feature or functionality foraffecting a change to the displayed document status. Alternatively,instead of providing a selectable control for accessing a given featureor functionality, information may be provided in the status pane as tothe identity and nature of available features that may be utilized foraffecting changes to the associated document status.

Referring still to FIG. 9, status information and associated applicationfeatures exposed via the document status panes 910-918 may include avariety of types of document status. For example, referring to thedocument status pane 910, information on a present security orprotection status of the document may be provided. For example, asillustrated in FIG. 9, if the present document has a security statusthat allows others to open and edit the document, a status string suchas “this document may be edited by others” may be provided in thedocument status pane 910 for alerting a user that the present securitystatus for the document allows others to edit the document rather thanthe document being in a “read-only” mode.

According to embodiments, in addition to providing the present status ofthe document, for example, the present security status of the document,information may be provided in the associated document status pane toalert the user that the user may make changes to the displayed status.For example, as illustrated in the document status pane 910, anadditional string of “you can prevent others from editing this document”is provided to alert the user that the user may affect changes to thepresent security status of the document. Thus, the status informationprovided in the status panes 910-918 is made richer by explaining to auser what the impact of a change in the status could be which willfurther promote the user's desire to use the available feature forchanging the present document status.

If an application feature is available for affecting changes to thedocument status, the application feature may be exposed in the documentstatus pane 910 in the form of a selectable control 911 for selectivelyaccessing the available feature. For example, a “manage protection”control 911 is illustrated in the document pane 910. After the userreads the present document's security status and learns that the presentdocument's security status may be changed, the user may select the“Manage Protection” control 911 for accessing the security features ofthe associated document editor application for making changes to thepresent security status. For example, the user may be allowed to encryptthe document, the user may be allowed to restrict formatting to thedocument, the user may be allowed to place the document in “read-only”mode, the user may be allowed to access an information rights management(IRM) application for setting various access and editing permissions ondocument, and the like. Advantageously, the user is provided usefulstatus information about the document, and where a feature orfunctionality is available for changing the present status of thedocument, access to the feature or functionality is exposed in proximityto the provided status information, as illustrated in FIG. 9.

Referring still to FIG. 9, other types of document status and associatedfeatures are illustrated. For example, the document status pane 912 isillustrated for notifying a user that harmful content may be in theassociated document and that the content has been disabled. Asillustrated in FIG. 9, an “Enable Content” control 913 is displayed inthe status pane 912 for allowing the user to selectively enable thecontent that has been otherwise disabled due to its suspected harmfulnature.

Another type of document status, illustrated in document status pane914, is whether the present document has been saved in a file formatthat is somehow incompatible or otherwise problematic in associationwith the present document editor version in use. For example, the in-usedocument editor may be a later version than the version with which theopened document was saved, and therefore, some application featuresotherwise available may not be available for use with the presentlyopened document unless the presently opened document is converted to thelater version. Accordingly, the status pane 914 may include a statusstring such as “you can upgrade this document's file format—somefeatures of your application are disabled because this document is savedusing an older file format—you can convert the current file format.”This display status text string not only provides the user with thepresent version status of the opened document, but alerts the user ofthe availability of a feature or functionality, for example, a documentconversion feature, for affecting a change to the present status of thedocument. According to this example, because a document conversionfeature is available, a “Convert Doc” control 915 may be displayed inthe status pane 914 to allow the user to selectively access the documentconversion feature for converting the opened document to the laterversion so that all of the features available to the later version ofthe document editor application may be used with the opened document.

The status pane 916 illustrates status information as to whether othersare currently editing the present document. The user is also notifiedthat he/she may contact other users of the document to coordinate withother users or otherwise communicate with other users of the document.As should be appreciated, this type of status may be provided when thedocument is available via a collaborative document sharing program thatallows one or more users, for example, users in a collaborative workteam, to open a given document and make edits to the document. Thestatus illustrated in status pane 916 may be used to notify a given userthat another user is currently editing the document, and an “Email orIM” control 917 may be provided for allowing the present user to sendand electronic mail or instant message to other users of the document.As should be appreciated, email or instant messaging are only examplesof two types of communication and are not limiting of other types ofcommunication systems that may be provided.

Referring still to FIG. 9, the document status pane 918 illustratesdocument status for notifying a user as to whether a document containsdigital signatures, or whether a document's digital signature have beeninvalidated or otherwise compromised. For example, if a previous userhas edited and finalized the present document, and has applied a digitalsignature to the document, the digital signature may be used to notifysubsequent users that the user who has applied the digital signature hasreviewed the document and has marked the document as final. The statusinformation illustrated in status pane 918 may be used to notify apresent user that such digital signature has been applied to thedocument. If the present user wishes to affect a change to the signatureinformation applied to the present document, a “Digital Signature”control 919 may be provided for allowing changes to the digitalsignature status of the document. Other associated controls such as the“Mark as Final” control 920 may be provided for allowing the user toapply a status to the document to alert subsequent users that thedocument has been finalized by a previous user.

As should be appreciated, the types of document status and theassociated selectable feature controls illustrated in FIG. 9 are forpurposes of example only, and are not limiting of the vast amounts andtypes of document status that may be displayed in a document status pane910-918, and are not limiting of the vast numbers of associated featuresand/or functionalities that may be exposed in the status panes 910-918for affecting changes to document status. For example, statusinformation and related features and/or functionalities may be exposedvia other document information panes available in the out-space userinterface. For example, referring back to FIG. 5, the print menu 508could be used to expose temporary print settings being applied to thedocument. In addition, the location and configuration of the statuspanes 910-918 and the feature controls 911-920 are not limiting of thedifferent orientations and layouts that may be utilized for providingthe information and associated feature controls in the out-space 202described herein.

According to an embodiment, information displayed in the document statuspanes 910-918 is dynamically maintained so that as associated statusinformation changes for a document, the information displayed in thestatus panes 910-918 and the selectable feature controls 911-920 exposedfor the associated status are changed as the document status changes.That is, as document status changes, a determination is made as towhether a different feature is available for use with the changedstatus, and if so, the different feature may be exposed with thedynamically updated status information. For example, referring to thestatus pane 910, if the presently edited document is in “read-only”mode, the status string may be changed to alert the user that thedocument is presently in “read-only” mode and that the user can changethe protection status of the document to allow others to edit thedocument.

According to an embodiment, the document status provided in the documentstatus panes 910-918 may be programmed to always be displayed when thedocument status tab 905 or other means for displaying document status isactuated, or individual types of document status or all document statusmay only be displayed when a given type of document status has changedor has met some threshold criteria for being displayed. For example,information associated with the disablement of harmful content, asillustrated in the status pane 912, may be programmed to only display inthe out-space if harmful content has been recently disabled. On theother hand, such status may be set for display at all times in theout-space 202 for alerting users of the potential of harmful content ina given document. That is, the document status may have a permanent homein the out-space user interface whether the status has changed or not,or the document status may be displayed in an associated document statuspane only when a change has occurred in the associated status. Foranother example, the digital signature information illustrated in thestatus pane 918 may be programmed such that the information is onlydisplayed if a change has occurred in the associated document thatinvalidates or otherwise compromises a previously applied digitalsignature.

FIG. 10 represents another example of an out-space user interfaceshowing a number of document status information panes and associatedapplication feature selection controls. A document status pane 1010 isillustrated in FIG. 10 showing a logical grouping of available featuresfor affecting a change to the present document status. The documentstatus illustrated in the status pane 1010 is associated with thepresent security status of the document. For example, the statusprovided in the pane 1010 alerts the user that the document may beedited by others, and that the user may change the editing permissionsapplied to the document with a number of different document protectionfeatures. Selectable controls 1011, 1012, 1013 are provided in theexpanded pane 1010 for providing the user access to the various documentprotection features available to the user for affecting a change to thepresent security status or editing permissions status of the document.For example, an “IRM” feature control 1011 may allow the user to applyvarious document editing permissions to the associated document.“Encrypt Document” control 1012 may allow the user to access a featurefor applying an encryption to the edited document, and a “RestrictFormatting” feature 1013 may allow the user to access a feature forrestricting formatting that may be applied to the document, for example,where the document is a standardized document that should not receiveformatting changes by various users having access to the document. Thus,one status pane may be used for exposing a variety of different featuresor for mapping a given type of status to a variety of differentfeatures.

Referring still to FIG. 10, the document status pane 916 is illustratedwith a border 1015 disposed around the perimeter of the status pane 916.According to an embodiment, status information provided in a givenstatus pane 910-918 may be designated with differing severity orimportance levels. According to one embodiment, the border 1015 may beused to highlight or color-code the associated status pane 916 foralerting a user as to the severity or importance level applied to thedisplayed status. For example, status of low importance may becolor-coded with a green border 1015, status information having a mediumseverity or importance level may be color-coded with a yellow border1015, and status information having a high severity or importance levelmay be color-coded with a red border 1015. For example, if a document isfound to contain harmful content, for example, an unknown macro orActiveX control, a status pane, such as status pane 912, illustrated inFIG. 9, may be provided having a border 1015 or other appropriateidentification mechanism for alerting the user that the statusinformation is of sever or high importance to the user. As should beappreciated, the color-coding and the use of a border 1015 are forpurposes of example only, and are not exhaustive of the many ways inwhich severity and/or importance levels may be indicated to a user. Forexample, a color-coded bar may be disposed along one end of the statuspane or along and upper or lower edge of the status pane. Likewise, avariety of importance-level icons, for example, flags, stars, and thelike, may be utilized for indicating severity and/or importance level.

FIG. 11 represents an exemplary operational flow diagram for accessingdocument status and associated application features via an out-spaceuser interface in a document editor program. Operational flow 1100begins at start operation 1102 and continues to operation 1104 where anin-space user interface is provided that includes an out-space actuator,as described above. For purposes of example, consider that theoperational flow 1100, illustrated in FIG. 11, is associated with auser's desire to obtain one or more types of document status for adocument being edited with the document editor 200.

Operational flow 1100 continues to decision operation 1106 where it isdetermined whether to enter the out-space user interface. If not,operational flow 1100 continues to decision operation 1108 where it isdetermined whether to exit the document editor. If it is determined toexit the document editor, operational flow continues to end operation1120. If it is determined to continue editing the document, operationalflow 1100 loops back. If the user has decided to enter the out-spaceuser interface for obtaining one or more types of document status,operational flow 1100 continues to operation 1110 where the out-spaceactuator is selected. When the out-space actuator is selected, thedocument may be converted to an image, the ribbon may be expanded, andout-space features may be populated in the user interface, asillustrated and described above. According to another embodiment, anddocument image may not be created.

At operation 1112, after selection of the document status tab 905 orother appropriate actuation method for displaying document status, oneor more types of document status may be displayed in associated documentstatus panes 910-918, 1010, as illustrated and described above withreference to FIGS. 9 and 10. In addition, if any features and/orfunctionalities are available for affecting change to displayed documentstatus, one or more selectable feature and/or functionality controls911-920, 1011-1013 may be displayed in the associated status panes, oralternatively, information about the identity and nature of availablefeatures or functionalities may be displayed in the status panes. Afterreview of the displayed status and any available associated features,operational flow continues to operation 1114, and a desirednon-authoring feature, for example, a feature for changing editingpermissions to the edited document, may be applied for changing theassociated status of the document.

According to an embodiment, after a given feature or functionality isutilized, the status information displayed in the associated status panemay be changed to reflect new status. For example, if based on thechange in status, the selected feature or functionality may no longer beapplicable, and therefore, that feature or functionality may be removedfrom the status pane. Alternatively, the associated status pane may beremoved from display after a change in status. Or, after a change instatus, the user may be automatically returned to the in-space userinterface.

After document status has been reviewed and changed, if desired,operation flow proceeds to operation 1118 for a return to the in-spaceuser interface or for an exit from the document editor. Operational flowends at operation 1120.

As described above with reference to FIGS. 1-11, a variety of documentinformation, including document status information may be provided viathe out-space user interface. As described below with reference to FIGS.12-14, communication between the out-space user interface and thein-space user interface is provided for alerting a user that informationpotentially of interest to the user is available in the out-space userinterface. FIG. 12 represents an example of an in-space user interfacehaving an out-space communication user interface component and having animproved message bar user interface component.

According to embodiments of the invention, information displayed in oneor more document information or status panes in the out-space userinterface is dynamically updated as associated information about thedocument changes. As illustrated in FIG. 12, an out-space communicationuser interface (UI) component 1210 is provided for communicatingdocument status information contained in the out-space user interface toalert a user that the information contained in the out-spacecommunication UI component represents a change in the document statusthat may be of interest to the user. For example, the out-spacecommunication UI component 1210, illustrated in FIG. 12, contains anexample text string 1215 of “Bob Smith has opened this document forediting.”

According to embodiments, the out-space communication UI component 1210temporarily displays in the in-space user interface to quickly relay thestatus information to alert the user that he/she should launch theout-space user interface to lean more about the status change of thedocument being edited. To allow the user to quickly launch the out-spaceuser interface, the out-space actuator 106 is displayed in closeproximity to or inside the out-space communication UI component 1210. Asshould be appreciated, the information contained in the temporarilydisplayed out-space communication UI component may be any informationabout the document that may be displayed in the out-space user interfaceas described herein with reference to FIGS. 1-15.

The out-space communication UI component 1210, illustrated in FIG. 12,is generally rectilinear in shape and contains the out-space actuator106 inside the UI component 1210. As should be appreciated, the shapeand orientation of the UI component 1210, illustrated in FIG. 12, is forpurposes of example only and is not limiting of the vast number ofshapes and orientations that may be used for the UI component 1210 andis not limiting of the locations at which the UI component 1210 may beplaced in the in-space user interface for alerting a user of associatedinformation contained in the out-space user interface.

According to one embodiment, the out-space communication UI component1210 may be visually highlighted, for example, color-coding, addition oficons, and the like, for indicating a severity or importance levelassociated with the information being communicated from the out-spaceuser interface. For example, a border 1220 disposed around the exampleUI component 1210 may be color-coded to indicate a severity orimportance level associated with the information being communicated fromthe out-space user interface.

According to one embodiment, the communication UI component 1210 may bedisplayed temporarily, for example, N seconds, after it becomes visible,and the amount of time for the display of the UI component may beincreased or decreased if desired. Alternatively, the UI component maybe manually dismissed by selecting (e.g., “clicking”) anywhere on the UIcomponent 1210. In addition, selecting the actuator 106 for displayingthe out-space user interface may cause an automatic dismissal of the UIcomponent 1210. If desired, presentation of the communication UIcomponent 1210 may be accompanied by an audible sound for furthercalling attention to the information displayed in the communication UIcomponent 1210.

Referring now to FIG. 13, if a user selects the out-space actuator 106displayed in or in proximity to the out-space communication UI component1210, the out-space user interface is automatically launched, asdescribed above, with reference to FIGS. 1-11. According to oneembodiment, a document information or document status pane 1316 thatcontains document information or status associated with thecommunication that was presented via the temporarily displayed out-spacecommunication UI component may be highlighted in a manner that brings auser's attention to the information or status pane 1316 associated withthe information that was communicated via the temporarily displayedout-space UI component.

For example, as illustrated in FIG. 13, the document status pane 1316contains information that another user has opened the document beingedited by the present user and provides the present user information onhow the user may check out the document or change the status of thedocument in response to the information provided to the present user. Toalert the user to the specific status pane associated with thecommunication provided to the user via the out-space communication UIcomponent 1210, a visual indication, for example, a highlighted brokenborder, is displayed around the associated information or task pane. Asshould be understood, a variety of visual indications may be utilizedfor drawing attention to a particular information or status paneassociated with the communication that was provided via thetemporarily-displayed out-space communication UI component. For example,information or status panes associated with communications provided viathe temporarily displayed out-space communication UI component may becolor-coded with a particular color, for example, green, to quicklyalert the user as to which information or status pane to review. Asdescribed above, color-coding may be used for information or statuspanes to indicate severity or importance levels associated with theinformation contained therein. To distinguish such visual indicationsfrom a visual indication used for associating a particular informationor status pane with the communication presented via the out-spacecommunication UI component 1210, a differing visual indication may beutilized.

Referring back to FIG. 12, a message bar 1225 is provided forcommunicating information from document information contained in theout-space user interface and for alerting a user of a potential need forlaunching the out-space user interface to review additional informationand to select one or more features or functionalities for affectingnon-authoring changes to the document being edited. As illustrated inFIG. 12, the message bar 1225 is displayed underneath the ribbon 102 andremains displayed until the message bar 1225 is dismissed by useraction, for example, by selecting the close button 1245. Informationdisplayed in the message bar 1225 may include an information subject1230 and an information summary 1235 for providing a subject andinformation summary of information communicated to the message bar 1225from the out-space user interface. According to one embodiment,selecting (e.g., clicking on) the message text 1235 will launch theout-space user interface to allow a user to review the associated statusinformation and to utilize any available features or functionalities, ifdesired. In addition, selectable controls 1240 may be provided in themessage bar 1225 for selectively obtaining one or more features and/orfunctionalities for receiving additional information or for changingstatus or properties associated with the document being edited.

An icon 1206 may be provided in the message bar 1225 for drawing auser's attention to the specific type of status information contained inthe out-space user interface that corresponds to the presently displayedmessage bar 1225. For example, if the status in the message bar isassociated with document security information in the out-space userinterface, the icon 1206 may be in a form that draws the user'sattention to a status pane containing security information.

For example, as illustrated in FIG. 12, an example information stringindicating that the present document contains and invalid digitalsignature is provided in the message bar 1225, and a selectable controlallowing the user to view signatures associated with the document isprovided. Thus, if the user selects the provided control 1240, the usermay be provided with the features or functionalities associated with adigital signature application to allow the user to view the digitalsignatures that have been applied to the document. As should beappreciated, the example information and selectable controls,illustrated in FIG. 12, are for purposes of illustration only and arenot limiting of the vast amount of information and features that may bemade available via the message bar 1225.

The shape and size of a message bar 1225 may be scaled to fit differentdisplay screens. That is, the message bar 1225 may be reduced in size ormay be expanded in size depending on the available display screen space.In addition, more than one message bar 1225 may be displayed asadditional information is communicated that may be of interest to theuser. That is, an additional message bar 1225 may be displayedunderneath the first message bar 1225 to communicate different types ofdocument information or status in a second displayed message bar 1225.

Referring now to FIG. 14, if the user selects the out-space actuator1206 displayed in or in proximity to the message bar 1225, the out-spaceuser interface is launched to allow the user to review additionalinformation and to obtain different features or functionalitiesassociated with the information that was communicated via the displayedmessage bar 1225. For example, as illustrated in FIG. 13, a documentstatus pane 1318 is shown to contain information corresponding to theinformation that was communicated to the in-space user interface via thedisplayed message bar 1225. As described above, a highlighting, forexample, color-coding, or other acceptable visual indication may be usedfor the corresponding information or status pane 1318 for allowing theuser to quickly determine the information or status pane containinginformation corresponding to the communication provided via thedisplayed message bar 1225.

As should be appreciated, a distinctive visual highlighting may beutilized for information or status panes 1318 associated withcommunications to the temporarily displayed out-space communication UIcomponent, and a different visual indication may be utilized forinformation or status panes associated with communications provided viathe displayed message bar 1225. Thus, when a user launches the out-spaceuser interface, the user may readily distinguish an information orstatus pane associated with the temporarily displayed communication UIcomponent as opposed to information communicated via the displayedmessage bar 1225. As illustrated in FIG. 13, the information associatedwith the temporarily displayed UI component is shown with a brokenoutlining border, and the status pane associated with the displayedmessage bar is visually highlighted with a solid border. Other visualindications may be utilized to give the information or status paneassociated with the temporarily displayed communication UI component aloud visual indication and for giving the information or status paneassociated with the displayed message bar a louder or loudest visualindication.

FIG. 14 represents an exemplary operational flow diagram for receiving acommunication of document status via an out-space communication userinterface component and via an improved message bar user interfacecomponent. For purposes of description of the operational flow diagramillustrated in FIG. 14, consider that a user of a given documentreceives information via the temporarily displayed out-spacecommunication UI component and/or via the displayed message bar userinterface component. Operation flow 1400 begins at operation 1402 andcontinues to operation 1404 where an in-space user interface is providedthat includes an out-space actuator. An example of an in-space userinterface may include FIG. 1. Operational flow 1400 continues todecision operation 1406 and a determination is made as to whether atemporary out-space communication UI component has been displayed. Ifnot, operational flow continues to operation 1418, as described below.

If a temporary out-space communication UI component 1225 is displayed,operational flow continues to operation 1410. At operation 1410, a usermay review information contained in the temporarily displayed out-spacecommunication UI component 1225, and if desired, the user may select theout-space actuator for launching the out-space user interface. Atoperation 1412, the user may review associated document status orinformation, and at operation 1414, the user may apply non-authoringfeatures and/or functionalities if desired. As described above, in orderto alert the user as to the particular information or status panecontained in the out-space user interface associated with thecommunication provided the temporarily displayed out-space communicationcomponent, the associated information or status pane contained in theout-space user interface may be visually highlighted in some manner toindicate its relationship to the information provided to the user viathe temporarily displayed out-space UI component.

At operation 1414, if the message bar 1225 is dynamically populated withinformation communicated from an associated information or status panecontained in the out-space user interface that is of interest to theuser, operational flow may proceed back to operation 1410, and the usermay launch the out-space user interface. At operation 1412, the user mayreview the associated document information or status pane, and atoperation 1414, the user may apply one or more features orfunctionalities available for changing document information or documentstatus provided in the out-space user interface. As described above, theassociated information or task pane displayed in the out-space userinterface associated with the information communicated to the user viathe message bar 1225 may be visually highlighted in some manner toquickly alert the user as to the particular information or status paneassociated with the information being provided to the user via themessage bar 1225. After the user has reviewed any information or statuscontained in the out-space user interface of interest to the user, theuser may return to the in-space user interface to continue editing thedocument, or the user may exit the document editor, and operational flowmay end at operation 1420. Thus, use of the temporarily displayedout-space communication UI component or the message bar UI componentallows for information to be communicated from the out-space userinterface to the in-space user interface to alert a user of a givendocument that information contained in the out-space user interface maybe of interest to the user.

By providing navigation between in-space and out-space, users may easilybecome familiar with out-space features because they are separated fromauthoring features. By separating in-space and out-space features, usersmay easily find features because the features are categorized. Featuresmay be richer and provide more information and functionality because the“real estate” of the display is better utilized. A greater amount of“real estate” is available for out-space features, thereby allowingsoftware developers the opportunity to increase the functionality of adocument editor program. Channels of communication associated with adocument are better managed because they are not mixed with in-spacefeatures.

Referring to FIG. 15, an exemplary system for implementing the inventionincludes a computing device, such as computing device 1500. In a basicconfiguration, computing device 1500 may include any type of stationarycomputing device or a mobile computing device. Computing device 1500typically includes at least one processing unit 1502 and system memory1504. Depending on the exact configuration and type of computing device,system memory 1504 may be volatile (such as RAM), non-volatile (such asROM, flash memory, and the like) or some combination of the two. Systemmemory 1504 typically includes operating system 1505, one or moreapplications 1506, and may include program data 1507. In one embodiment,applications 1506 further include application 1520 for accessing anout-space user interface. This basic configuration is illustrated inFIG. 15 by those components within dashed line 1508.

Computing device 1500 may also have additional features orfunctionality. For example, computing device 1500 may also includeadditional data storage devices (removable and/or non-removable) suchas, for example, magnetic disks, optical disks, or tape. Such additionalstorage is illustrated in FIG. 15 by removable storage 1509 andnon-removable storage 1510. Computer storage media may include volatileand non-volatile, removable and non-removable media implemented in anymethod or technology for storage of information, such as computerreadable instructions, data structures, program modules or other data.System memory 1504, removable storage 1509 and non-removable storage1510 are all examples of computer storage media. Computer storage mediaincludes, but is not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bycomputing device 1500. Any such computer storage media may be part ofdevice 1500. Computing device 1500 may also have input device(s) 1512such as a keyboard, mouse, pen, voice input device, touch input device,etc. Output device(s) 1514 such as a display, speakers, printer, etc.may also be included.

Computing device 1500 also contains communication connection(s) 1516that allow the device to communicate with other computing devices 1518,such as over a network or a wireless network. Communicationconnection(s) 1516 is an example of communication media. Communicationmedia typically embodies computer readable instructions, datastructures, program modules or other data in a modulated data signalsuch as a carrier wave or other transport mechanism and includes anyinformation delivery media. The term “modulated data signal” may includea signal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media may include wired media such asa wired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. The term computerreadable media as used herein includes both storage media andcommunication media.

Although the invention has been described in language that is specificto structural features and/or methodological steps, it is to beunderstood that the invention defined in the appended claims is notnecessarily limited to the specific features or steps described. Rather,the specific features and steps are disclosed as forms of implementingthe claimed invention. Since many embodiments of the invention can bemade without departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

What is claimed is:
 1. A computer-readable storage medium, implementedin hardware, including computer-executable instructions forcommunicating status information for a document from an out-space userinterface to an in-space user interface for alerting a user of thedocument of the availability of the status information in the out-spaceuser interface, comprising: displaying an in-space user interface thatincludes a display of authoring features and a document display area forcreating and editing a document and an out-space actuator associatedwith the out-space user interface, and displaying a document that iseditable in the document display area of the in-space user interface;receiving a status of the document, and saving the status of thedocument in the out-space user interface; performing at least one of:temporarily displaying in the in-space user interface an out-spacecommunication user interface (UI) component for alerting a user of thedocument about the availability of the status of the document; ordisplaying in the in-space user interface a message bar for alerting auser of the document about the availability of the status of thedocument; and disposing the out-space actuator in the out-spacecommunication user interface (UI) component for allowing deployment ofthe out-space user interface that includes: removing the display of theeditable document that is displayed within the document display areaassociated with the in-space user interface; and displaying anon-authoring feature within the document display area in response toselection of the out-space actuator from the out-space communicationuser interface (UI) component for allowing the user of the document toreview the status of the document.
 2. The computer-readable storagemedium of claim 1, further comprising: receiving a selection of theout-space actuator from the out-space communication user interface (UI)component or receiving a selection of the out-space actuator from themessage bar; in response to receiving the selection of the out-spaceactuator displaying the out-space user interface; and displaying thestatus of the document in the out-space user interface.
 3. Thecomputer-readable storage medium of claim 2, further comprising:displaying the status of the document in a document status display panethat is displayed in the out-space user interface; and visuallyhighlighting the document status display pane to indicate that thestatus of the document displayed in the document status display pane foralerting a user of the document about the availability of the status ofthe document.
 4. The computer-readable storage medium of claim 1,wherein temporarily displaying in the in-space user interface anout-space communication user interface (UI) component for alerting auser of the document about the availability of the status of thedocument includes displaying in the out-space communication userinterface (UI) component information that communicates at least aportion of the status of the document saved in the out-space userinterface to the user of the document.
 5. The computer-readable storagemedium of claim 3, further comprising: determining a non-authoringfeature that may be utilized for changing the status of the document;and displaying information about the feature that may be utilized forchanging the status of the document in the out-space user interface withthe displayed status of the document.
 6. The computer-readable storagemedium of claim 5, further comprising displaying a selectable control inthe document status display pane for accessing the feature for changingthe status of the document.
 7. The computer-readable storage medium ofclaim 6, further comprising applying a secondary visual indication tothe document status display pane to indicate an importance levelassociated with the displayed status of the document.
 8. Thecomputer-readable storage medium of claim 3, further comprising:dynamically updating the status of the document displayed in thedocument status display pane as the status of the document changes.
 9. Asystem for communicating status information for a document from anout-space user interface to an in-space user interface for alerting auser of the document of the availability of the status information inthe out-space user interface, comprising: a processing unit and acomputer-readable storage medium; the processing unit configured toperform actions, comprising: displaying an in-space user interface thatincludes a display of authoring features and a document display area forcreating and editing a document and an out-space actuator associatedwith the out-space user interface, and displaying a document that iseditable in the document display area of the in-space user interface;receiving a status of the document, and saving the status of thedocument in the out-space user interface; performing at least one of:temporarily displaying in the in-space user interface an out-spacecommunication user interface (UI) component for alerting a user of thedocument about the availability of the status of the document; ordisplaying in the in-space user interface a message bar for alerting auser of the document about the availability of the status of thedocument; and disposing the out-space actuator in the out-spacecommunication user interface (UI) component for allowing deployment ofthe out-space user interface that includes: removing the display of theeditable document that is displayed within the document display areaassociated with the in-space user interface; and displaying anon-authoring feature within the document display area in response toselection of the out-space actuator from the out-space communicationuser interface (UI) component for allowing the user of the document toreview the status of the document.
 10. The system of claim 9, furthercomprising: receiving a selection of the out-space actuator from theout-space communication user interface (UI) component or receiving aselection of the out-space actuator from the message bar; in response toreceiving the selection of the out-space actuator displaying theout-space user interface; and displaying the status of the document inthe out-space user interface.
 11. The system of claim 10, furthercomprising: displaying the status of the document in a document statusdisplay pane that is displayed in the out-space user interface; andvisually highlighting the document status display pane to indicate thatthe status of the document displayed in the document status display panefor alerting a user of the document about the availability of the statusof the document.
 12. The system of claim 9, wherein temporarilydisplaying in the in-space user interface an out-space communicationuser interface (UI) component for alerting a user of the document aboutthe availability of the status of the document includes displaying inthe out-space communication user interface (UI) component informationthat communicates at least a portion of the status of the document savedin the out-space user interface to the user of the document.
 13. Thesystem of claim 11, further comprising: determining a non-authoringfeature that may be utilized for changing the status of the document;and displaying information about the feature that may be utilized forchanging the status of the document in the out-space user interface withthe displayed status of the document.
 14. The system of claim 13,further comprising displaying a selectable control in the documentstatus display pane for accessing the feature for changing the status ofthe document.
 15. The system of claim 14, further comprising applying asecondary visual indication to the document status display pane toindicate an importance level associated with the displayed status of thedocument.
 16. The system of claim 11, further comprising: dynamicallyupdating the status of the document displayed in the document statusdisplay pane as the status of the document changes.
 17. A system forcommunicating status information for a document from a secondary userinterface to a primary interface for alerting a user of the document ofthe availability of the status information in the secondary userinterface, comprising: a processing unit and a computer-readable storagemedium; the processing unit being configured to perform actions,comprising: providing a primary user interface having an actuatorassociated with the secondary user interface, and displaying a documentin the primary user interface; receiving a first status of the document,and saving the first status of the document in the secondary userinterface; temporarily displaying in the primary user interface anout-space communication user interface (UI) component for alerting auser of the document about the availability of the first status of thedocument; disposing the actuator associated with the secondary userinterface in the out-space communication user interface (UI) componentfor allowing deployment of the secondary user interface in response toselection of the actuator from the out-space communication userinterface (UI) component for allowing the user of the document to reviewthe status of the document; displaying in the primary user interface amessage bar for alerting a user of the document about the availabilityof a second status of the document saved in the secondary userinterface; and disposing the actuator associated with the secondary userinterface in the message bar for allowing deployment of the out-spaceuser interface that replaces a display of the document within a documentdisplay area of the primary user interface used to display the documentin response to selection of the actuator from the message bar forallowing the user of the document to review the second status of thedocument.
 18. The system of claim 17, wherein the processing unit isconfigured to perform actions, further comprising: displaying the firstand second statuses of the document in respective first and seconddocument status display panes that are displayed in the secondary userinterface; and visually highlighting each of the first and second statusdisplay panes with a different visual highlighting to indicate that thefirst status of the document displayed in the first document statusdisplay pane is associated with the out-space communication userinterface (UI) component temporarily displayed in the primary userinterface, and to indicate that the second status of the documentdisplayed in the second document status display pane is associated withthe message bar displayed in the primary user interface.
 19. The systemof claim 17, wherein temporarily displaying in the in-space userinterface an out-space communication user interface (UI) component foralerting a user of the document about the availability of the status ofthe document includes displaying in the out-space communication userinterface (UI) component information that communicates at least aportion of the status of the document saved in the out-space userinterface to the user of the document.
 20. The system of claim 19,wherein the processing unit is configured to perform actions, furthercomprising: dynamically updating the first and second statuses of thedocument displayed in each of the first and second document statusdisplay panes as the first and second statuses of the document change;temporarily displaying in the primary user interface an updatedout-space communication user interface (UI) component for alerting auser of the document about the availability of the updated first statusof the document; and updating information displayed in the displayedmessage bar for alerting a user of the document about the availabilityof the updated second status of the document.